$ type MMS024.RELEASE_NOTES


 






                      RELEASE NOTES FOR VAX DEC/MMS VERSION 2.4

                      RELEASE NOTES FOR VAX DEC/MMS VERSION 2.4

                      RELEASE NOTES FOR VAX DEC/MMS VERSION 2.4



          1  VAX DEC/MMS ON VMS AND MicroVMS

          1  VAX DEC/MMS ON VMS AND MicroVMS

          1  VAX DEC/MMS ON VMS AND MicroVMS

          VAX DEC/MMS Version 2.4 is supported on VMS Version 4.6 or
          higher.

          For VMS Version 5.0 (or higher) systems, the following VMS
          classes are required for full functionality of MMS:


          o  VMS Required Saveset
          o  Utilities

          o  Programming Support

          For more information on VMS classes and tailoring, refer to the
                                                               .

          _______ _________ ______ ________ _______ ___________

          VAX/VMS Operating System Software Product Description


          For MicroVMS V4.x systems, the following components of MicroVMS
          are required for full functionality of MMS:


          o  Base System

          o  Program development










                                                                         1

                                                                         1

                                                                         1





















 






          2  INSTALLATION OF VAX DEC/MMS

          2  INSTALLATION OF VAX DEC/MMS

          2  INSTALLATION OF VAX DEC/MMS

          The Installation Verification Procedure (IVP) is now provided
          as a separate file, SYS$TEST:MMS$IVP.COM. You can run the IVP
          separately from the installation procedure. If you're installing
          MMS on a VAXcluster, perform the following steps on each node in
          the cluster licensed to run MMS:


          o  Replace the DCLTABLES image with the INSTALL utility as
             follows:


                  $ INSTALL = "$INSTALL/COMMAND"
                  $ INSTALL REPLACE SYS$SHARE:DCLTABLES


          o  Invoke the IVP:

                  @SYS$TEST:MMS$IVP



          3  BUGS FIXED

          3  BUGS FIXED

          3  BUGS FIXED

          The following bugs were fixed in VAX DEC/MMS Version 2.4.


          o  During the installation of VAX DEC/MMS, the Installation
             Verification Procedure (IVP) hung if VAX DEC/CMS was on the
             system but CMSPROSHR.EXE was not installed. This problem has
             been corrected.







          2

          2

          2




































 






          o  Locking problems occurred when two or more running MMS de-
             scriptor files tried to access the same file at the same
             time. MMS sometimes aborted with the following error message:

                  %MMS-F-NOACCESS, Unable to access file "file-name"
                  -RMS-E-FLK, File currently locked by another user


             This problem occurred most frequently when multiple MMS
             descriptor files were running in batch, and access was made
             to files that are common to all. Our analysis has shown that
             MMS did not permit file sharing when the file was opened.
             For Version 2.4 calls, all functions that open a file for
             read-only access were changed to specifically allow file
             sharing.



          4  DOCUMENTATION ERRATA

          4  DOCUMENTATION ERRATA

          4  DOCUMENTATION ERRATA

                                                        contains the

          ___ _____ __ ___ __________ __________ ______

          The Guide to VAX DEC/Module Management System
          following documentation errors and omissions:


          o  The informal example on page 2-3 should have the continua-
             tion character (-) before the comment line on line 2 of the
             example:


             TEST1.BAS, - ! Source modules for TESTS.OBJ


          o  Example 3-4 has a syntax error. ("MMS$TARGET") should be
             replaced by ("$(MMS$TARGET)"). There are three occurrences on
             page 3-23, lines 2 and 4, and three occurrences on page 3-25,
             lines 25 and 27.



                                                                         3

                                                                         3

                                                                         3




































 






          o  The second paragraph of section 4.1.2 omitted the word "is".
             The paragraph should read:

             "For example, CRTLIB(C$STRLEN=STRLEN.OBJ) designates that
             module C$STRLEN is in library CRTLIB.OLB; C$STRLEN is found
             in the file named STRLEN.OBJ."


          o  Section 2.8 describes the actions MMS will take if a source
             dependency is omitted in a rule. The documentation suggests
             that MMS will invoke the built-in rules to build the target
             based on the filenames being the same.


             The documentation should also state that if you enter:

                  a.obj depends_on b.for


             and omit the action line, MMS will not know how to build
             the target. MMS will then issue the error "actions to update
             target are unknown".


          o  Section 2.8.6 should state that if you want MMS to access
             a CMS library, all of the file types that could come from
             the library must also be present in the suffix list. The
             section should also include a reference to Table C.4, the MMS
             Suffixes Precedence List.


          o  Section 3.1 describes double colon dependencies. The follow-
             ing example is shown on page 3-2.






          4

          4

          4




































 






                  MOD2.OBJ, MOD3.OBJ :: DEFS1.DEF  ! If at least one source is
                       PRINT DEFS1.DEF             ! newer than targets, print
                                                   ! DEFS1.DEF

                  MOD2.OBJ :: DEFS2.DEF            ! If MOD2.PAS or DEFS2.DEF
                       PASCAL MOD2                 ! is newer than MOD2.OBJ,
                                                   ! compile MOD2.PAS


             That example works as long as DEFS2.DEF or MOD2.PAS is newer
             than MOD2.OBJ and DEFS1.DEF. However, that is the normal be-
             havior of MMS. Double colon dependencies work as they should,
             but section 3.1 should state that they are not especially
             useful in most cases.



          5  RESTRICTIONS

          5  RESTRICTIONS

          5  RESTRICTIONS

          The following restrictions apply to VAX DEC/MMS Version 2.4.


          o  VAX DEC/MMS Version 2.4 does not support the use of VAX
             DEC/CMS Version 1.


          o  The MMS subprocess always uses DCLTABLES as its CLITABLE.
             This occurs because the subprocess is activated via LIB$SPAWN
             which, though it does allow specification of a CLI, does
             not allow specification of CLITABLES. A workaround to this
             problem is to put an explicit SET COMMAND/TABLE=alternate_
             table as a .FIRST directive in the MMS description file.


          o  It is entirely possible that expansion of the macro
             $(MMS$CHANGED_LIST) will result in a string that is too large
             to be handled by the CLI; this is a restriction imposed by
             the CLI itself.

                                                                         5

                                                                         5

                                                                         5




































 








          o  MMS cannot get the time stamps for files that are opened as
             writeable and shared. The result is that MMS assumes the file
             doesn't exist, and will always fire the needed rules to build
             the file and all targets that depend on it as a source. MMS
             Version 2.4 issues the following fatal error message when it
             tries to get the time stamp of a locked file.


                  %MMS-F-NOACCESS, Unable to access file "<filename>".
                  -RMS-E-FLK, file currently locked by another user
             There are two workarounds to this problem:


             -  Maintain and build against an .OLB library of the file
                while linking against the shared image, or


             -  Remove either the write or shared attributes of the file
                during the MMS build.


          o  Use of the CMSFLAGS macro in combination with /GENERATION
             after a tilde (~) in a dependency can cause MMS to look
             up the latter generation but then attempt a FETCH of the
             generation specified in the CMSFLAGS macro. Occlusion will
             be handled properly. You cannot use CMSFLAGS to override
             generation and occlusion information explicitly placed in
             the dependency. To avoid fetching a different generation from
             what was looked up, you should include "/GEN=$&" in the value
             of CMSFLAGS. If you do not override the MMS-supplied default
             CMSFLAGS, the correct generation will be FETCHed.






          6

          6

          6




































 






          o  When /SCA_LIBRARY has been specified and the directory
             pointed to by $(SCALIBRARY) exists but is not yet an SCA
             library, MMS requires a second subprocess for its spawn of
             SCA to create the library. If the subprocess quota is insuf-
             ficient to do the spawn, MMS will stop with a Quota Exceeded
             message. Increasing the process's subprocess quota, PRCLM, by
             1 will eliminate the problem.


          o  When MMS is used with the /CMS qualifier, MMS does not prop-
             erly use the file SYS$INPUT as the /DESCRIPTOR file unless
             there is a colon (:) following the filename. For example:


                  MMS/CMS/DESCRIPTOR=SYS$INPUT

             should be changed to

                  MMS/CMS/DESCRIPTOR=SYS$INPUT:


          o  When the DEC/SHELL command DCC is used from MMS, MMS does not
             terminate after a compilation error. The workaround is to use
             the DCL command CC.















                                                                         7

                                                                         7

                                                                         7


$ 

